-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[ML] Fix infer on and elasticsearch service endpoint created with a deployment id #121428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi @davidkyle, I've created a changelog YAML for you. |
|
Pinging @elastic/ml-core (Team:ML) |
| model.getServiceSettings().getNumThreads(), | ||
| model.getServiceSettings().modelId(), | ||
| model.getServiceSettings().getAdaptiveAllocationsSettings(), | ||
| model.getServiceSettings().getDeploymentId(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the fix. The rest of the changes are removing constructors or reducing the visibility of the ctors so that it is not possible to make this mistake
dan-rubinstein
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…eployment id (elastic#121428) Fixes a bug where the deployment Id was lost creating the text embedding model configuration
…eployment id (elastic#121428) Fixes a bug where the deployment Id was lost creating the text embedding model configuration
…eployment id (elastic#121428) Fixes a bug where the deployment Id was lost creating the text embedding model configuration
💔 Backport failed
You can use sqren/backport to manually backport by running |
…eployment id (elastic#121428) (elastic#121440) Fixes a bug where the deployment Id was lost creating the text embedding model configuration # Conflicts: # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/elasticsearch/ElasticsearchInternalService.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/elasticsearch/ElserInternalServiceSettings.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/elasticsearch/MultilingualE5SmallInternalServiceSettings.java # x-pack/plugin/inference/src/test/java/org/elasticsearch/xpack/inference/services/elasticsearch/ElasticsearchInternalServiceTests.java
…eployment id (#121428) (#121440) (#121514) Fixes a bug where the deployment Id was lost creating the text embedding model configuration # Conflicts: # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/elasticsearch/ElasticsearchInternalService.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/elasticsearch/ElserInternalServiceSettings.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/services/elasticsearch/MultilingualE5SmallInternalServiceSettings.java # x-pack/plugin/inference/src/test/java/org/elasticsearch/xpack/inference/services/elasticsearch/ElasticsearchInternalServiceTests.java
When creating an inference endpoint with the Elasticsearch service the
deployment_idservice setting can be used connect to an existing ml trained model deployment. A bug was found where inference on an endpoint created this way would fail with the errorCould not find trained model [X]. The problem was that thedeployment_idsetting was lost when updating the service settings with the text embedding dimensions.The bug only applied to Text Embedding models uploaded with the Eland
eland_import_hub_modelscript.The bug could be easily reproduced with these steps: